Personalized delivery time estimate system

ABSTRACT

A personalized delivery estimate system is described. A commercial transaction is generated between a seller and a buyer for an item in an online marketplace. Historical transactions of buyers and sellers in the online marketplace are stored in a storage device. A personalized delivery time estimate is computed for the buyer of the commercial transaction using seller information, buyer information, and item information with the historical transactions of buyers and sellers in the online marketplace.

CLAIM OF PRIORITY

This Application is a Continuation of U.S. application Ser. No.13/436,618, filed Mar. 30, 2012, which is hereby incorporated byreference in its entirety.

TECHNICAL FIELD

This application relates generally to the field of computer technologyand, in a specific example embodiment, to a system and method for apersonalized delivery date estimate.

BACKGROUND

Websites provide a number of publishing, listing, and price-settingmechanisms whereby a publisher (e.g., a seller) may list or publishinformation concerning items for sale. Once a buyer places an order foran item, the seller fulfills the order by shipping the item to thebuyer.

The buyer, eager to receive the item, is provided a time range estimatethat typically spans from several days to a week. Such poor shippingdelivery estimate accuracy can create frustration in the buyer from notknowing when exactly to expect receipt of the item. Such a poorexperience can result in the buyer reducing purchases from the sellerand reducing visits to the publisher.

BRIEF DESCRIPTION OF THE DRAWINGS

The present description is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings in which:

FIG. 1 is a network diagram depicting a network system, according to oneembodiment, having a client-server architecture configured forexchanging data over a network;

FIG. 2 is a block diagram illustrating an example embodiment of apersonalized delivery estimate application;

FIG. 3 is a flow diagram illustrating an example embodiment of a processfor a personalized delivery estimate application;

FIG. 4 is a flow diagram illustrating another example embodiment of aprocess for a personalized delivery estimate application;

FIG. 5 is a flow diagram illustrating an example embodiment of a methodfor computing a delivery date estimate;

FIG. 6 is a flow diagram illustrating another example embodiment of amethod for computing a delivery date estimate; and

FIG. 7 shows a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions may beexecuted to cause the machine to perform any one or more of themethodologies discussed herein.

DETAILED DESCRIPTION

Although the embodiments have been described with reference to specificexample embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader spirit and scope of the description. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

In various embodiments, a personalized delivery estimate system isdescribed. A commercial transaction is generated between a seller and abuyer for an item in an online marketplace. Historical transactions ofbuyers and sellers in the online marketplace are stored in a storagedevice. A personalized delivery time estimate is computed for the buyerof the commercial transaction using seller information, buyerinformation, and item information with the historical transactions ofbuyers and sellers in the online marketplace.

FIG. 1 is a network diagram depicting a network system 100, according toone embodiment, having a client-server architecture configured forexchanging data over a network. For example, the network system 100comprises a network-based publisher 102, where clients may communicateand exchange data within the network system 100. The data may pertain tovarious functions (e.g., online item purchases) and aspects (e.g.,managing order information) associated with the network system 100 andits users. Although illustrated herein as a client-server architectureas an example, other embodiments may include other networkarchitectures, such as a peer-to-peer or distributed networkenvironment.

A data exchange platform, in an example form of the network-basedpublisher 102, may provide server-side functionality, via a network 104(e.g., the Internet), to one or more clients. The one or more clientsmay include users that utilize the network system 100 and, morespecifically, the publication/publisher system 102, to exchange dataover the network 104. These transactions may include transmitting,receiving (communicating), and processing data to, from, and regardingcontent and users of the network system 100. The data may include, butare not limited to, content and user data such as order and shippingtracking information; item information; user profiles, user attributes;user reputation values; product and service reviews and information(such as pricing and descriptive information); product, service,manufacturer, and vendor recommendations and identifiers; product andservice listings associated with buyers and sellers; auction bids; andtransaction data, among other things.

In various embodiments, the data exchanges within the network system 100may be dependent upon user-selected functions available through one ormore client or user interfaces (UIs). The UIs may be associated with aclient machine, such as a client machine 106 using a web client (e.g.,web browser) 110. The web client 110 may be in communication with thenetwork-based publisher 102 via a web server 120. The UIs may also beassociated with a client machine 108 using a programmatic client 112,such as a client application. It can be appreciated that in variousembodiments, the client machines 106 and 108 may be associated with abuyer, a seller, a third party electronic commerce platform, and/or apayment service provider. The buyers and sellers may be any one ofindividuals, merchants, or service providers, among other things.

Furthermore, a shipping carrier server 132 of a shipping serviceprovider may be in communication with the network-based publisher 102and optionally with client machines 106 and 108. The shipping carrierserver 132 includes a shipping carrier application 116 to provide ashipping tracking mechanism to the client machines 106 and 108 and anapplication server 122 of the network-based publisher 102. The shippingtracking mechanism allows the client machines 106 and 108 and theapplication server 122 to determine a status of a shipment for an itemassociated with an order placed by a buyer of the network-basedpublisher 102.

Turning specifically to the network-based publisher 102, an applicationprogram interface (API) server 118 and a web server 120 are coupled to,and provide programmatic and web interfaces respectively to, one or moreapplication servers 122. The application servers 122 host a publicationapplication 124 and a personalized delivery estimate module 130. Theapplication servers 122 are, in turn, shown to be coupled to one or moredatabase server(s) 126 that facilitate access to one or more database(s)128.

In one embodiment, the web server 120 and the API server 118 communicateabout and receive data pertaining to listings, transactions, ordertracking information, and feedback, among other things, via various userinput tools. For example, the web server 120 may send and receive datato and from a toolbar or webpage on a browser application (e.g., webclient 110) operating on a client machine (e.g., client machine 106).The API server 118 may send and receive data to and from an application(e.g., web client 110 or shipping carrier application 116) running onanother client machine (e.g., shipping carrier server 132).

The publication application 124 may provide a number of publisherfunctions and services (e.g., listing, payment, etc.) to users thataccess the network-based publisher 102. For example, the publicationapplication 124 may provide a number of services and functions to usersfor listing goods and/or services for sale, facilitating transactions,and reviewing and providing feedback about transactions and associatedusers. The publication application 124 may further report a shipmentstatus related to a transaction. In one embodiment, the publicationapplication 124 includes an online marketplace. The online marketplacemay generate a commercial transaction between a seller and a buyer foran item listed in the online marketplace.

The personalized delivery estimate module 130 generates a personalizeddelivery time estimate to a buyer of the online marketplace for an itemsold by a seller. The personalized delivery time estimate may include adate and time estimate, a range of dates, and a range of dates andtimes. The personalized delivery estimate module 130 may generate apersonalized delivery time estimate for the buyer of the commercialtransaction using seller information, buyer information, and iteminformation with the historical transactions of buyers and sellers inthe online marketplace. An embodiment of the personalized deliveryestimate module 130 is further described below.

FIG. 2 is a block diagram illustrating an example embodiment of thepersonalized delivery estimate module 130. In one embodiment, thepersonalized delivery estimate module 130 includes a buyer module 202, aseller module 204, a transaction item module 206, a marketplacetransaction history module 208, a shipping service provider module 210,a seasonal module 212, and a personal delivery estimate computationengine 214.

The buyer module 202 determines a shipping delivery geographic locationusing the buyer information from the publication application 124. Forexample, the buyer information may include a name, a physical address(i.e., street name/post office box and zip code), an email address, anda telephone number. In particular, the buyer information may alsoinclude a mailing address. For example, the buyer may wish to have theitem ordered on the online marketplace shipped to a particular deliveryaddress or location. The buyer information may be stored in a storagedevice, such as the database 128.

The seller module 204 determines a shipping origin geographic locationusing the seller information from the publication application 124. Forexample, the seller information may include a name, a physical address(i.e., street name/post office box and zip code), an email address, anda telephone number. In particular, the seller information may alsoinclude an origin address. For example, the seller may ship the itemfrom a warehouse or a location other than the seller address registeredon the online marketplace. The seller information may be stored in astorage device, such as the database 128.

The transaction item module 206 identifies the item to be shipped andspecifications of a shipping package based on the identified item. Forexample, the transaction item module 206 may identify an item with itsname, weight, physical dimensions, and model number. The specificationsof the shipping package may include a weigh of the shipping package andphysical dimensions of the shipping package to fit the item. Thespecification of the shipping package may be determined or extrapolatedfrom the identification of the item. For example, if the item to beshipped is a printer, the dimensions and weight of the printer may beobtained from the model number. The dimensions of the shipping containermay then be obtained from the dimensions and weight of the printer.

In another embodiment, the seller may be prompted to provide thetransaction item module 206 with the specifications of the shippingpackage.

In yet another embodiment, the physical specifications of the item mayinclude, for example, physical dimensions (e.g., height, width, length,and weight). Physical dimensions may be deduced or derived, for example,from a picture or video of the item taken with a mobile device of theseller.

The marketplace transaction history module 208 identifies historicaldelivery times (e.g., elapsed time from order placed to item received)using the historical transactions of buyers and sellers in the onlinemarketplace of the item and the historical transactions of the seller inthe online marketplace. The historical transactions of buyers andsellers in the online marketplace may be stored in a storage device,such as database 128.

The historical transactions of buyers and sellers may include buyerinformation, seller information, origin address, shipping address, itemsshipped, shipping service provider, shipping and handling elapsed time(e.g., how long did it take from the time the buyer placed the order tothe time the item was delivered to the buyer), handling time (e.g., howlong it took the seller to deposit the item with the shipping carrier),shipping duration (e.g., how long was the time in transit with theshipping carrier), and data and time of delivery.

In another embodiment, the marketplace transaction history module 208identifies historical transactions of buyers having a shipping originwithin a first threshold distance of the shipping origin of the buyer,and sellers having a shipping destination within a second thresholddistance of the shipping destination of the seller, for items havingspecifications similar to a specification of the item. In other words,the marketplace transaction history module 208 identifies previoustransactions involving similar items that were shipped from a similargeographic source location to a similar geographic destination location.The marketplace transaction history module 208 then computes an averageshipping and handling time using the identified historical transactions.To refine the estimate, the marketplace transaction history module 208may further identify similar shipping carriers with similar selectedshipping services.

In another embodiment, the marketplace transaction history module 208computes an average handling time for the seller to ship the item usingthe historical delivery times. The handling time comprises a timeelapsed from when an order is received by the seller from the onlinemarketplace to when the item is shipped by the seller.

In yet another embodiment, the historical transactions of the sellerinclude seller ratings, seller feedbacks, and a number of items shippedon the online marketplace from the seller.

The shipping service provider module 210 determines a shipping carrierdelivery estimate using the seller information, the buyer information,specifications of the shipping package, and a selected shipping service.For example, given the origin address, the destination address, and theselected shipping service (e.g., first class, expedited delivery, rush,priority, next day, ground, express, and so forth), the shipping serviceprovider module 210 communicates with the corresponding shipping serviceprovider to obtain a delivery estimate based on the above input. Forexample, the shipping service provider may determine that it takes 5-7days to ship the item from a first location to a second location. Itshould be noted that the shipping carrier delivery estimate does notinclude the handling time: the elapsed time between the time an order isreceived by the seller and the time the item is provided to (or pickedup by) the shipping service provider for shipping by the seller. Inanother embodiment, the handling time may include the elapsed timebetween the time an order is received and the time the shipping serviceprovider is notified to pick up the item.

The seasonal module 212 determines a shipping season and any otherexternal factors affecting a shipping duration of the item. For example,weather and holidays may affect shipping time. Other factors may includeemployees' strikes, power outages, fuel shortages, and so forth.

The personal delivery estimate computation engine 214 generates thepersonalized delivery time estimate for the buyer using the shippingdelivery geographic location, the shipping origin geographic location,historical delivery times, the shipping carrier delivery estimate, theshipping season, and external factors. The personalized delivery timeestimate comprises a range of dates.

For example, the personal delivery estimate computation engine 214 maydetermine how long it typically takes for a similar item to be shippedfrom a seller to a buyer with similar zip code, similar shippingcarrier, and similar shipping carrier service.

In another example, the personal delivery estimate computation engine214 may look at prior transactions from the seller to determine onaverage how long it typically takes for the seller to prepare an itemfor shipping. For example, it may take, on average, 1.5 days for aseller to ship the item from the time the order has been received.

In another embodiment, a further analysis may be performed based on thetype of item being shipped. For example, some items may take a longertime to prepare for shipping (such as fragile items since they requiremore packaging and preparation).

In another embodiment, different weights may be assigned to the shippingdelivery geographic location, the shipping origin geographic location,historical delivery estimates, the shipping carrier delivery estimate,the shipping season, and external factors to compute the personalizeddelivery time estimate for the buyer.

For example, the historical delivery estimates may carry a heavierweight in computing the personalized delivery time estimate for thebuyer than the shipping carrier delivery estimate.

FIG. 3 is a flow diagram 300 illustrating an example embodiment of aprocess for a personalized delivery estimate application. At operation302, a shipping origin and destination are determined. For example, theshipping origin and destination may be determined from the commercialtransaction between a seller and a buyer in an online marketplace. Theseller may ship the item from a particular geographic origin location.The buyer may wish to receive delivery of the item at a particulargeographic destination location. In one embodiment, the operation 302may be implemented using the buyer module 202 and the seller module 204.

At operation 304, the shipping specifications, shipping carrier, andshipping service are determined. In one embodiment, the information fromthe commercial transaction in the online marketplace may be used todetermine the weight and dimension of a shipping container for theordered item. The shipping carrier and the shipping service (e.g.,express or regular) may also be determined from the commercialtransaction. In one embodiment, the operation 304 may be implementedusing the transaction item module 206.

At operation 306, a personalized delivery date and time estimate may becomputed using the previous information (from the buyer module 202, theseller module 204, and the transaction item module 206) by comparing andmining data from the marketplace transaction history module 208. Inother words, personalized delivery estimates may be generated by lookingat similar transactions (e.g., same origin zip code, same destinationzip code, same shipping carrier, and same shipping service) from theprior history of transactions to better determine and estimate adelivery date.

FIG. 4 is a flow diagram 400 illustrating another example embodiment ofa process for a personalized delivery estimate application. At operation402, shipping origin and destination are determined. For example, theshipping origin and destination may be determined from the commercialtransaction between a seller and a buyer in an online marketplace. Theseller may ship the item from a particular geographic origin location.The buyer may wish to receive delivery of the item at a particulargeographic destination location. In one embodiment, the operation 402may be implemented using the buyer module 202 and the seller module 204.

At operation 404, the shipping specifications, shipping carrier, andshipping service are determined. In one embodiment, the information fromthe commercial transaction in the online marketplace may be used todetermine the weight and dimension of a shipping container for theordered item. The shipping carrier and the shipping service (e.g.,express or regular) may also be determined from the commercialtransaction. In one embodiment, the operation 404 may be implementedusing the transaction item module 206.

At operation 406, the shipping carrier generates a first estimatedshipping delivery date based on the provided information. It should benoted that that shipping carrier may use their own database and shippingestimate algorithm to generate their own estimates. The presentdisclosure seeks to further refine the estimated shipping delivery dateby mining the data from the historical transactions on the onlinemarketplace. For example, instead of a delivery estimate of 2-5 days,the personal delivery estimate computation engine 214 may provide anarrower and more precise delivery estimate (e.g., 3-4 days).

At operation 408, the personal delivery estimate computation engine 214generates a second estimated shipping delivery date based on the datafrom the historical transactions on the online marketplace. In oneembodiment, the first estimated shipping delivery date is adjusted usingthe second estimated delivery date. In another embodiment, an averageestimated shipping delivery date may be generated based on a median, oraverage, of the first estimated delivery date and the second estimateddelivery date.

FIG. 5 is a flow diagram 500 illustrating an example embodiment of amethod for computing a delivery date estimate. At operation 502, thepersonal delivery estimate computation engine 214 searches themarketplace transaction history module 208 to retrieve an averagedelivery time (e.g., 3.5 days) from shipping origin to a shippingdestination with a same zip code, a same shipping carrier, a sameshipping service, and a same item. In another embodiment, zip codeswithin a threshold radius of the zip code from the shipping destinationof the item from the commercial transaction may be used. Items similarin size and weight may also be identified.

At operation 504, the average delivery time is adjusted usingtransaction history from the same seller with the personalized deliveryestimate computation engine 214. For example, the transaction historymay include seller feedback, number of items shipped, handling time, andso forth. Each of these factors are weighted to adjust (increase ordecrease) the average delivery time. For example, the average deliverytime may decrease when the item is sold by a seller with mostly positivefeedback. The average delivery time may decrease based on the averagehandling time it takes the seller to package and ship items.

Alternative embodiments include retrieving the average delivery time bycategory/size/weight/dimensions/values of items corresponding to theactual item to be shipped. For example, the seller transactions historymay indicate that the average handling time for high value items (valueof items exceeding a threshold) may be 1.2 days whereas the averagehandling time for low value items (value of items below a threshold) maybe 1.8 days. Based on those observations, the average delivery time maybe tuned and refined.

At operation 506, the adjusted average delivery time computed inoperation 504 is further adjusted based on conditions presentsurrounding the time of shipping with the personalized delivery estimatecomputation engine 214. For example, there may be a snow storm includingzip codes neighboring the zip code of the destination shipping address.Such a snow storm may create a delay. As such, the adjusted averagedelivery time from operation 504 may be further adjusted to reflect thesnow storm conditions. Other conditions may include labor strikes, roadconditions, fuel shortages, or any other disrupting current conditionsat the time of shipping that may affect the shipping delivery time.

At operation 508, the re-adjusted average estimated delivery date may becommunicated to the buyer once the order has been placed. In anotherembodiment, to further improve accuracy of the estimated delivery date,the estimated delivery date is computed upon the seller acknowledgingreceipt of the order. In a further embodiment, to further improveaccuracy of the estimated delivery date, the estimated delivery date iscomputed after the seller submits the shipping package containing theitem to the shipping carrier.

FIG. 6 is a flow diagram 600 illustrating another example embodiment ofa method for computing a delivery date estimate. At operation 602, thepersonal delivery estimate computation engine 214 assigns differentweights to each different factor (e.g., seller feedback, total number ofitems shipped on the online marketplace (and/or other marketplaces),handling time elapsed on the online marketplace (and/or othermarketplaces), shipping season (Christmas time, Valentine's Day, and soforth), and shipping carrier performance.

In another embodiment, the personal delivery estimate computation engine214 may recommend that the seller utilize the shipping services ofanother carrier based on the shipping carrier performance computed bymining the database of the online marketplace for historicaltransactions.

At operation 604, the personalized delivery estimate computation engine214 computes an estimated delivery based on the weighted factors.

Certain embodiments described herein may be implemented as logic or anumber of modules, engines, components, or mechanisms. A module, engine,logic, component, or mechanism (collectively referred to as a “module”)may be a tangible unit capable of performing certain operations andconfigured or arranged in a certain manner. In certain exampleembodiments, one or more computer systems (e.g., a standalone, client,or server computer system) or one or more components of a computersystem (e.g., a processor or a group of processors) may be configured bysoftware (e.g., an application or application portion) or firmware (notethat software and firmware can generally be used interchangeably hereinas is known by a skilled artisan) as a module that operates to performcertain operations described herein.

In various embodiments, a module may be implemented mechanically orelectronically. For example, a module may comprise dedicated circuitryor logic that is permanently configured (e.g., within a special-purposeprocessor, application specific integrated circuit (ASIC), or array) toperform certain operations. A module may also comprise programmablelogic or circuitry (e.g., as encompassed within a general-purposeprocessor or other programmable processor) that is temporarilyconfigured by software or firmware to perform certain operations. Itwill be appreciated that a decision to implement a module mechanically,in dedicated and permanently configured circuitry, or in temporarilyconfigured circuitry (e.g., configured by software) may be driven by,for example, cost, time, energy-usage, and package size considerations.

Accordingly, the term “module” should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which modules orcomponents are temporarily configured (e.g., programmed), each of themodules or components need not be configured or instantiated at any oneinstance in time. For example, where the modules or components comprisea general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differentmodules at different times. Software may accordingly configure theprocessor to constitute a particular module at one instance of time andto constitute a different module at a different instance of time.

Modules can provide information to, and receive information from, othermodules. Accordingly, the described modules may be regarded as beingcommunicatively coupled. Where multiples of such modules existcontemporaneously, communications may be achieved through signaltransmission (e.g., over appropriate circuits and buses) that connectthe modules. In embodiments in which multiple modules are configured orinstantiated at different times, communications between such modules maybe achieved, for example, through the storage and retrieval ofinformation in memory structures to which the multiple modules haveaccess. For example, one module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further module may then, at a later time,access the memory device to retrieve and process the stored output.Modules may also initiate communications with input or output devicesand can operate on a resource (e.g., a collection of information).

FIG. 7 shows a diagrammatic representation of a machine in the exampleform of a computer system 700 within which a set of instructions may beexecuted causing the machine to perform any one or more of themethodologies discussed herein. In alternative embodiments, the machineoperates as a standalone device or may be connected (e.g., networked) toother machines. In a networked deployment, the machine may operate inthe capacity of a server or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine may be a personal computer (PC), atablet PC, a set-top box (STB), a personal digital assistant (PDA), acellular telephone, a web appliance, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The example computer system 700 includes a processor 702 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 704 and a static memory 706, which communicate witheach other via a bus 708. The computer system 700 may further include avideo display unit 710 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). The computer system 700 also includes analphanumeric input device 712 (e.g., a keyboard), a UI navigation device714 (e.g., a mouse), a disk drive unit 716, a signal generation device718 (e.g., a speaker) and a network interface device 720.

The disk drive unit 716 includes a machine-readable medium 722 on whichis stored one or more sets of instructions and data structures (e.g.,software 724) embodying or utilized by any one or more of themethodologies or functions described herein. The software 724 may alsoreside, completely or at least partially, within the main memory 704and/or within the processor 702 during execution thereof by the computersystem 700, with the main memory 704 and the processor 702 alsoconstituting machine-readable media.

The software 724 may further be transmitted or received over a network726 via the network interface device 720 utilizing any one of a numberof well-known transfer protocols (e.g., HTTP).

While the machine-readable medium 722 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstores the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present description or that is capable of storing,encoding or carrying data structures utilized by or associated with sucha set of instructions. The term “machine-readable medium” shallaccordingly be taken to include, but not be limited to, solid-statememories, optical media, and magnetic media. Specific examples ofmachine-readable storage media include non-volatile memory, including byway of example semiconductor memory devices (e.g., Erasable ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM), and flash memory devices); magnetic disks such asinternal hard disks and removable disks; magneto-optical disks; andCD-ROM and DVD-ROM disks.

What is claimed is:
 1. A system, comprising: a processor and executableinstructions accessible on a computer-readable medium that, whenexecuted, cause the processor to perform operations comprising:generating a commercial transaction between a seller and a buyer for anitem in an online marketplace; identifying a shipping attribute from thecommercial transaction; retrieving a first estimated delivery date froma shipping carrier server based on the shipping attribute; identifying ahistorical transaction having a historical shipping attribute matchingthe shipping attribute of the commercial transaction; determining asecond estimated delivery date based on historical delivery timesassociated with the historical transaction; adjusting the secondestimated delivery date based on transaction history of the seller;generating a personalized delivery time estimate for the buyer for theitem of the commercial transaction based on the first estimated deliverydate and the second estimated delivery date; calculating anitem-specific average handling time for the seller based on shippeditems with a similar weight and similar physical dimensions to the item;calculating an item-specific average shipping time of the shipped itemssimilar to a shipping weight and shipping dimensions of the item betweena shipping origin geographic location and a shipping delivery geographiclocation with a similar shipping carrier and a similar shipping serviceof the similar shipping carrier based on the historical transaction;adjusting the personalized delivery time estimate for the buyer of thecommercial transaction based on the item-specific average handling timefor the seller and the item-specific average shipping time; and causingdisplay of the personalized delivery time estimate on a user interfaceof a client machine associated with the buyer.
 2. The system of claim 1,wherein the shipping attribute includes one or more of a shipping origingeographic location, a shipping delivery geographic location, a shippingweight and shipping dimensions of the item, a shipping carrier, or ashipping service of the shipping carrier.
 3. The system of claim 1,wherein the item-specific; average handling time comprises an averagetime elapsed from when an order is received by the seller from theonline marketplace to when the item is shipped by the seller.
 4. Thesystem of claim 1, wherein the transaction history of the sellerincludes seller ratings, seller feedbacks, and a number of items shippedon the online marketplace from the seller.
 5. The system of claim 2,wherein the operations further comprise: determining the shippingdelivery geographic location using buyer information; determining theshipping origin geographic location using seller information; andidentifying the item and specifications of a shipping package based onthe identified item, the specifications of the shipping packagecomprising a weight of the shipping package and physical dimensions ofthe shipping package.
 6. The system of claim 5, wherein the operationsfurther comprise: determining a shipping carrier delivery estimate usingthe seller information, the buyer information, the specifications of theshipping package, and the shipping service of the shipping carrier. 7.The system of claim 6, wherein the operations further comprise:determining a shipping season and external factors affecting a shippingtime of the item.
 8. The system of claim 7, wherein the personalizeddelivery time estimate is determined based on the shipping season andthe external factors, the personalized delivery time estimate comprisinga range of dates.
 9. The system of claim 1, wherein different weightsare assigned to the first estimated delivery date and the adjustedsecond estimated delivery date when computing the personalized deliverytime estimate.
 10. A method comprising: generating a commercialtransaction between a seller and a buyer for an item in an onlinemarketplace; identifying a shipping attribute from the commercialtransaction; retrieving a first estimated delivery date from a shippingcarrier server based on the shipping attribute; identifying a historicaltransaction having a historical shipping attribute matching the shippingattribute of the commercial transaction; determining a second estimateddelivery date based on historical delivery times associated with thehistorical transaction; adjusting the second estimated delivery datebased on transaction history of the seller; generating a personalizeddelivery time estimate for the buyer for the item of the commercialtransaction based on the first estimated delivery date and the secondestimated delivery date; calculating an item-specific average handlingtime for the seller based on shipped items with a similar weight andsimilar physical dimensions to the item; calculating an item-specificaverage shipping time of the shipped items similar to a shipping weightand shipping dimensions of the item between a shipping origin geographiclocation and a shipping delivery geographic location with a similarshipping carrier and a similar shipping service of the similar shippingcarrier based on the historical transaction; adjusting the personalizeddelivery time estimate for the buyer of the commercial transaction basedon the item-specific average handling time for the seller and theitem-specific average shipping time; and causing display of thepersonalized delivery time estimate on a user interface of a clientmachine associated with the buyer.
 11. The method of claim 10, whereinthe shipping attribute includes one or more of a shipping origingeographic location, a shipping delivery geographic location, a shippingweight and shipping dimensions of the item, a shipping carrier, or ashipping service of the shipping carrier.
 12. The method of claim 10,wherein the item-specific average handling time comprises an averagetime elapsed from when an order is received by the seller from theonline marketplace to when the item is shipped by the seller.
 13. Themethod of claim 10, wherein the transaction history of the sellerincludes seller ratings, seller feedbacks, and a number of items shippedon the online marketplace from the seller.
 14. The method of claim 11,further comprising: determining the shipping delivery geographiclocation using buyer information; determining the shipping origingeographic location using seller information; and identifying the itemand specifications of a shipping package based on the identified item,the specifications of the shipping package comprising a weight of theshipping package and physical dimensions of the shipping package. 15.The method of claim 14, further comprising: determining a shippingcarrier delivery estimate using the seller information, the buyerinformation, the specifications of the shipping package, and theshipping service of the shipping carrier.
 16. The method of claim 15,further comprising: determining a shipping season and external factorsaffecting a shipping time of the item, and wherein the personalizeddelivery time estimate is determined based on the shipping season andthe external factors, the personalized delivery time estimate comprisinga range of dates.
 17. The method of claim 16, wherein different weightsare assigned to the first estimated delivery date and the adjustedsecond estimated delivery date when computing the personalized deliverytime estimate.
 18. A non-transitory computer-readable storage mediumstoring a set of instructions that, when executed by a hardwareprocessor, cause the hardware processor to perform operationscomprising: generating a commercial transaction between a seller and abuyer for an item in an online marketplace; identifying a shippingattribute from the commercial transaction; retrieving a first estimateddelivery date from a shipping carrier server based on the shippingattribute; identifying a historical transaction having a historicalshipping attribute matching the shipping attribute of the commercialtransaction; determining a second estimated delivery date based onhistorical delivery times associated with the historical transaction;adjusting the second estimated delivery date based on transactionhistory of the seller; generating a personalized delivery time estimatefor the buyer for the item of the commercial transaction based on thefirst estimated delivery date and the second estimated delivery date;calculating an item-specific average handling time for the seller basedon shipped items with a similar weight and similar physical dimensionsto the item; calculating an item-specific average shipping time of theshipped items similar to a shipping weight and shipping dimensions ofthe item between a shipping origin geographic location and a shippingdelivery geographic location with a similar shipping carrier and asimilar shipping service of the similar shipping carrier based on thehistorical transaction; adjusting the personalized delivery timeestimate for the buyer of the commercial transaction based on the item:specific average handling time for the seller and the item-specificaverage shipping time; and causing display of the personalized deliverytime estimate on a user interface of a client machine associated withthe buyer.